@david-hummingbot @rapcmia will be nice to test this PR with the dashboard and mcp

Commit 6c09578

• Setup dev mode of hummingbot-api + dashboard on source ok
• Added binance and check portfolio page
• Run endpoint portfolio/history:

  curl -X 'POST' \
    'http://localhost:8000/portfolio/history' \
    -u admin/admin \
    -H 'Content-Type: application/json' \
    -d '{
        "limit": 100,
        "interval": "5m",
        "account_names": ["master_account"],
        "connector_names": ["binance"]
  
  }'
  

• Tested on intervals {5m, 15, and 30m} ✅
  
  • Compared all intervals and confirmed each response contains unique data
  • Build docker image and run tests on hummingbot-mcp by calling requesting “give me history portfolio 15m” ✅
    
• Tested on invalid interval (3m), getting response ✅

  "msg": "Value error, Invalid interval '3m'. Must be one of: ['5m', '15m', '30m', '1h', '4h', '12h', '1d']",
  "input": "3m",
  

• Compared with current hummingbot-api
  
  • Run two separate instance of curl and compare, all dataset the same
  • Time diff of 2mins before running the other curl still same response

incase needed, attached test logs:
11262025a.zip

Pending:

• Had not tested dashboard as I cannot see which part i can test the intervals like on hummingbot-api or hummingbot-mcp